Since version 2.04 the vobsub utils install as unicode under Win2k/XP+.
The supported unicode text file is UTF-16LE (little endian byte order).
To create a new file as unicode (or trasform an existing into it) you should (re)save it with notepad after selecting "UNICODE" as the "Encoding" on the Save As dialog.
Update 2.09+:
- You can convert to or from unicode easily by using subresync. Just be sure to always choose the right character set. Note: DEFAULT character set means your local Windows setting.
The benefits:
- Every tool supports regular and unicode text files both as their input. This means while you can create textual subtitles containing characters from dozens of languages at the same time (arabic, asian, latin, ...), there is absolutely no need to mess with codepages. However there is an exception: ssa supports a kind of mixed format, refer to demo.ssa of the subtitler plugin for VitrtualDub.
- You can use characters, can only be represented by two bytes, in the path or the file name.
The disadvantages:
- Since windows 9x doesn't support most of the unicode part of the windows API, you won't be able to use/watch unicode files under those operating systems.
- "Submux"-ed unicode files will work under win9x, but not guaranteed to be correct.
